📌 Summary

This PR prepares depkeeper v0.1.0 for its first stable release.

It introduces a configuration system, enhances test coverage and structure, updates documentation across the project, improves CLI behavior, and changes the default version pinning strategy for dependency updates.

🧩 What Does This PR Change?

🚀 Core Features

• Added config.py with support for:

  • depkeeper.toml
  • pyproject.toml

• ⚠️ BREAKING: Changed default version specifier from >= to ==

• Improved CLI error handling, logging, and context management

• Added Windows development setup script (scripts/setup_dev.ps1)

• Updated version from 0.1.0.dev3 → 0.1.0

🧪 Testing Improvements

• Added:

  • test_config.py
  • test_context.py
  • test_main.py

• Expanded coverage for:

  • conflict model
  • package model
  • requirement model
  • data store

• Introduced test markers:

  • unit
  • integration
  • e2e
  • slow
  • network

• Refactored tests to consistent Arrange-Act-Assert structure

• Added Copilot testing guidelines

📚 Documentation Updates

• Updated:

  • Installation guide
  • Quickstart
  • Basic usage
  • Checking updates
  • Updating dependencies
  • CI/CD integration
  • Configuration guide
  • Troubleshooting

• Updated README with:

  • Configuration examples
  • Version pinning explanation

• Updated changelog under Unreleased

🐛 Bug Fixes

• Fixed check command exit code (now succeeds even if updates are available)
• Removed redundant decorator from check command

🎯 Motivation

This release establishes the v0.1.0 stable baseline with:

1. Configurable behavior via project-level configuration files
2. Deterministic dependency updates through exact version pinning
3. Improved reliability via expanded unit testing
4. Production-ready CLI error handling
5. Windows development support

This provides a stable foundation for future feature expansion.

🧪 How to Test This

Configuration Testing

echo '[depkeeper]
check_conflicts = true
strict_version_matching = false' > depkeeper.toml

depkeeper check --verbose

Expected: configuration file is detected and applied.

Version Pinning Behavior

depkeeper update requests
grep "requests==" requirements.txt

Expected: dependency is pinned using ==.

Cross-Platform Setup

Windows

.\scripts\setup_dev.ps1

Linux/macOS

./scripts/setup_dev.sh

Test Suite

pytest -v -m unit
pytest --cov
pytest

All tests should pass.

✔️ Checklist

Code Quality

• My code follows depkeeper’s style guidelines
• I ran mypy and resolved type issues

Testing

• I added or updated unit tests
• All tests pass (pytest)
• I added/updated test fixtures if needed
• Added test markers for better organization

Documentation

• I updated documentation (if this PR changes APIs, behaviors, or commands)
• I updated examples (CLI / Python)
• I added/updated changelog entry (under Unreleased)

Backwards Compatibility

• This change is backward compatible
• OR this PR includes a clear description of breaking changes

⚠️ Breaking Changes

Version Specifier Behavior

Default update behavior changed:

Before:

requests>=2.31.0

After:

requests==2.31.0

Users preferring minimum specifiers can:

• Use --min-specifier (if available)
• Manually edit requirements files after update

🔍 Related Issues

• Establishes v0.1.0 stable release baseline
• Implements configuration system requirements